Jump to content

2.3.1 => 2.3.2 changed files only?


Guest tidyhost

Recommended Posts

We are pleased to announce the release of IP.Board 2.3.2, IP.Gallery 2.2.1, and IP.Converge 1.0.0

IP.Board 2.3.2

This release is a bug fix and maintenance release for IP.Board. While there are skin changes to fix skin-related bugs, those changes are not critical. There is no need to revert your custom skin changes on upgrade if you are not experiencing problems.



You can download the latest release of IP.Board in your client area. If you are currently running IP.Board 2.3.1

there is a changed files only download in the client area.

Link to comment
Share on other sites

Where is the list with all the bug fixes?

As IPS wrote - there's an announcement for changes


Yeah I mentioned that in my topic. Would also be nice if they include a gallery skin differences set too.



Changed files since IP.Board 2.3.1
  • cache
    • lang_cache
      • en
        • acp_lang_acpperms.php
        • lang_email_content.php
        • lang_error.php
        • lang_global.php
        • lang_javascript.js
        • lang_msg.php
        • lang_post.php
        • lang_register.php
        • lang_topic.php
        • lang_ucp.php
  • converge_local
    • converge.php
  • interface
    • board
      • index.php
      • modules
        • ipb
          • api.php
          • config.php
          • index.html
          • methods.php
  • ips_kernel
    • class_ajax.php
    • class_api_server.php
    • class_db.php
    • class_db_mysql_client.php
    • class_db_mysqli_client.php
    • class_difference.php
    • class_image.php
    • class_upload.php
    • class_xml.php
    • class_xml_rpc.php
  • jscripts
    • ipb_global.js
    • ipb_register.js
    • ips_ipsclass.js
    • ips_menu.js
    • ips_profile_portal.js
    • ips_text_editor.js
    • ips_text_editor_lite.js
  • lofiversion
    • index.php
  • resources
    • components.xml
    • help_sections.xml
    • help_settings.xml
    • ipb_skin-pro.xml.gz
    • ipb_templates.xml
    • settings.xml
    • version_history.php
  • skin_acp
    • IPB2_Standard
      • acp_css.css
      • acp_skin_html
        • cp_skin_api.php
        • cp_skin_dashboard.php
        • cp_skin_member.php
      • images
        • folder_components
          • xmlrpc
            • api_user.png
            • index.html
            • log_row.png
  • sources
    • acp_loaders
      • acp_admin.php
      • acp_pages_admin.php
    • action_admin
      • acppermissions.php
      • api.php
      • components.php
      • dashboard.php
      • diagnostics.php
      • forums.php
      • languages.php
      • login.php
      • login_auth.php
      • member.php
      • moderator.php
      • paysubscriptions.php
      • postoffice.php
      • rebuild.php
      • remote_template.php
      • rssexport.php
      • rssimport.php
      • security.php
      • settings.php
      • skin_import.php
      • skin_template_bits.php
      • sql_mysql.php
    • action_public
      • announcements.php
      • calendar.php
      • forums.php
      • login.php
      • messenger.php
      • misc
        • legends.php
        • warn.php
      • moderate.php
      • profile.php
      • register.php
      • topics.php
      • usercp.php
      • xmlout.php
    • api
      • api_components.php
      • api_core.php
      • api_forums.php
      • api_member.php
      • api_settings.php
      • api_skins.php
      • api_tasks.php
      • api_topic_view.php
      • api_topics_and_posts.php
    • classes
      • attach
        • class_attach.php
        • plugin_msg.php
        • plugin_post.php
      • bbcode
        • class_bbcode.php
        • class_bbcode_core.php
      • class_display.php
      • class_email.php
      • class_forums.php
      • class_session.php
      • editor
        • class_editor_rte.php
      • paymentgateways
        • class_gw_2checkout.php
        • class_gw_authorizenet.php
        • class_gw_manual.php
        • class_gw_nochex.php
        • class_gw_paypal.php
        • class_gw_protx.php
        • class_gw_safshop.php
        • class_gw_test.php
      • post
        • class_post.php
        • class_post_edit.php
        • class_post_reply.php
    • components_public
      • profile
        • posts.php
        • topics.php
    • handlers
      • han_editor.php
      • han_parse_bbcode.php
      • han_paysubscriptions.php
    • ipsclass.php
    • lib
      • admin_forum_functions.php
      • func_mod.php
      • func_msg.php
      • func_topic_threaded.php
      • func_usercp.php
      • search_mysql_ftext.php
      • search_mysql_man.php
      • tar.php
    • loginauth
      • convert
        • auth.php
        • auth_sha256.php
      • external
        • auth.php
      • ipconverge
        • auth.php
      • ldap
        • auth.php
      • login_core.php
    • portal_plugins
      • calendar.php
      • recent_topics.php
    • sql
      • mysql_queries.php
      • mysql_subsm_queries.php
    • tasks
      • dailycleanout.php
  • style_images
    • 1
      • folder_editor_images
        • css_rte.css
  • upgrade
    • core
      • actions
        • install.php
Link to comment
Share on other sites

You'd spend more time manually patching your files to save your mods, than manually reinstalling your mods afterwards


Probably true. Although a lot of changed files sure are files which a lot of mods edit.

On most upgrades I haven't had to spend as long putting my mods back in again, but this was kind of a killer. Because 1. I didn't properly note some file edits I amde on my own and had to look at my old files to figure out what I even did. and 2. It was hard to keep up with everything and make sure I got everything in since I was guessing which mods used which files. So I had to pretty much go through all of my mods and make sure on which files they needed to edit.

Oh also a mod to find a member's posts in topics (by ntd then upgraded by .will) well the query info which was said to change.... the original was different now so I had to look closely to be sure I changed it properly and kept the IPB changes in tact. In fact 3 times I had to be careful since IPB had differing lines than when the mods were made.


Long story short: some mods have to be upgraded even for this point release.
Link to comment
Share on other sites

Yes, but on the other hand we waited a decent amount of time since the last update. The longer we wait between updates, the longer you can go without reapplying modifications, however the bigger the update then becomes (requiring you to spend more time reapplying the modifications when do eventually release).

We try to keep a proper balance as much as possible.

Link to comment
Share on other sites

I appreciate your waiting, because I'm sure that most users don't want to have to run upgrades all the time or have to re-install their modifications, like you said. I know that it takes a *lot* of effort on the part of the Invision staff to compile the huge list of manual patches to the files--I've made a few public modifications and even just the documentation for those can take ages.

On my board, I've made probably twenty or thirty distinct modifications on my own that I haven't made documentation for. If I had to, I could, but I'd rather avoid that if at all possible. I also have another fifteen or so modifications taken from various websites. I could re-install all of these, but I'd rather just overwrite the files that aren't typically ever modified (everything but sources and maybe jscripts) and manually patch the ones that are. Even if IPS could come out with just the manual patches for the files that are usually modified, that'd be great.

If that's more trouble than it's worth for you guys, I totally understand.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...